Plan a minor update

Minor updates are ingested into Golden Gate as an update to an existing project. Although, technically, minor updates can be done at any time, it’s best to follow these guidelines:

• For newly added assignments and activities, make sure that these are seeded in PAF and DAALT BEFORE doing a minor content update. Any existing assignments and activities should already be seeded in PAF and DAALT. (Seeding takes place during Brix publication via the Digital Publishing Workbench [DPW].)
• Avoid deploying a minor content update during prime usage time.

  This can reduce the chance of confusion or complications for users. Consider doing a minor content update within the first month of deployment.

• To avoid potential user data loss, try to minimize the number of minor updates.
• With each minor update, errors can be introduced and users may even lose notes and highlights. This is only an issue when you change the number of characters within a paragraph.
• If you delete a whole paragraph, its notes will be orphaned and will not display. If you replace this deleted paragraph with a new paragraph, the new paragraph will not have any attached notes if you used the Paragraph identifier in the notes. If you used the Dom element structure, the new paragraph might get the deleted paragraph's notes.
• Updates require time and resources. Work with your editorial team to plan an appropriate number of updates for a given title.

If you are making a minor update and the title was deployed after March of 2017, all settings in Mission Bay will be preserved. However, if the title was pushed live before March of 2017, you must make note of all Mission Bay settings before undeploying the title and reenter them when you redeploy it.